Andre,
This behaviour can make updates go lost without there being any reason to have a save conflict!
Watch this :
- Agent creates NotesDocumentCollection
- User opens a document thats in the collection and updates field 'Field_A'
- User saves document
- Agent fetches same document that the user allready has saved!
- Agents updates field 'Field_B' (in fact it doesn't have to change anything, saving the document is enough)
- Agent saves the document --> There is no reason for a save conflict here, because the user had already closed and saved this document before the agent fetched the document.
- The update of field 'Field_A' by the user is lost.
Joris
Return to top
. . . . No, this is not about save conflict... (~Dan Brefreepul... 10.Oct.03) 
Print this page
